I have a doors module which was created two years ago and lot of changes made on it. But the history tab for most of the objects are empty.. Can anyone provide me the information in what are all the cases the history entry for object in a module won't be available? like while copying or archive and importing the module etc... BrownK - Wed Aug 28 00:22:52 EDT 2013 |
Re: why no history entries found for objects in the module? History can be turned off. - Check Attribute Definitions History is stored in baselines and restarted in the 'current'. - Check baselines for History History can be lost by Archive-Restore if baselines are not archived. -Adam |
Re: why no history entries found for objects in the module? Adamarla - Wed Aug 28 02:43:01 EDT 2013 History can be turned off. - Check Attribute Definitions History is stored in baselines and restarted in the 'current'. - Check baselines for History History can be lost by Archive-Restore if baselines are not archived. -Adam Clarify: when you Baseline a module, history is stored in the Baseline and the "current" module has no History (well, except the "Baseline" History itself). This makes the module load faster and this is a major reason to do minor baselines on big busy modules. Some History is "read-locked". Example: If you create attr "A" and then delete it, attr "A" no longer exists and nobody has any "R"ead acces to it, and the two History (create/Delete) will be "read-locked". To overcome this, routinely log in as the "Administrator" to view History. I don't think History is copied when you "copy-paste" or "clone" (copy-paste-special) a module. When you delete a module-baseline you lose all History stored therein. I hate it when that happens. If you create an object with say AbsNo 4 and then close the module without saving, there will be no History for object 4 (which doesn't exist) but the next object created will be 5. History of Links is a database configuration option. Clever evil folks can remove the History file of a module directly from the database file hierarchy. -Louie |
Re: why no history entries found for objects in the module? llandale - Wed Aug 28 14:30:03 EDT 2013 Clarify: when you Baseline a module, history is stored in the Baseline and the "current" module has no History (well, except the "Baseline" History itself). This makes the module load faster and this is a major reason to do minor baselines on big busy modules. Some History is "read-locked". Example: If you create attr "A" and then delete it, attr "A" no longer exists and nobody has any "R"ead acces to it, and the two History (create/Delete) will be "read-locked". To overcome this, routinely log in as the "Administrator" to view History. I don't think History is copied when you "copy-paste" or "clone" (copy-paste-special) a module. When you delete a module-baseline you lose all History stored therein. I hate it when that happens. If you create an object with say AbsNo 4 and then close the module without saving, there will be no History for object 4 (which doesn't exist) but the next object created will be 5. History of Links is a database configuration option. Clever evil folks can remove the History file of a module directly from the database file hierarchy. -Louie I suggest that DOORS has fallen over whilst performing a save. You will probably find you have a major discrepancy in the size of history.dtc and history.dtb, and the temporary history file history.dtn may be present. If this is the case you can try copying history.dtb over the top of history.dtc, you may find your history comes back. Obviously you should do a backup before messing around with backend files. Richard |